New base classes allow iParts to inherit features for both the run-time and design-time controls. These shared features can enhance the functioning of every iPart that inherits them:
■ Configuration options, such as setting collapsing behavior and assigning a CSS class, which is handy for designers to use to control the display of individual iParts
■ User interface, such as a standard layout for runtime controls and a standard, skinnable options block for commands and drop-down list options:
■ Run-time properties, such as EntityManager (which can run SOA functions) and user type checking: UserId, IsProxied (for the new On Behalf Of feature), IsAnonymousUser
■ Programmatic control, such as disabling design-time validation and handling SOA errors
Base classes help to future-proof iParts: when new features are added to the base classes, iParts inherit them and can make use of them immediately.
Numerous iParts already take advantage of these new base classes. When you create new iParts, make them inherit from these base classes so that you can make full use of the expanding set of shared functionality and the ability to control your iPart using CSS. You can also update your existing iParts to take advantage of these new base classes.